Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1715

reference
786-tree-1
name
1715
tree-preservation-order

undefined

786-tpo-1
uprn
address-text
point
POINT (-1.038492 50.865250)
geometry
MULTIPOLYGON (((-1.038393 50.865240,-1.038398 50.865259,-1.038411 50.865277,-1.038433 50.865291,-1.038461 50.865300,-1.038491 50.865303,-1.038522 50.865300,-1.038550 50.865292,-1.038572 50.865278,-1.038587 50.865261,-1.038592 50.865241,-1.038588 50.865222,-1.038574 50.865204,-1.038552 50.865190,-1.038525 50.865181,-1.038494 50.865177,-1.038463 50.865180,-1.038435 50.865189,-1.038413 50.865203,-1.038398 50.865220,-1.038393 50.865240)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL